Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d30aa04f0bd3bb35796c719fb05fda46acad9321ee858d65dfd02a0f02fcbeda

Tx prefix hash: 93b518c3acbd4d45b2475819c6af93a120428e94ad84b2b618b9f68d0964582d
Tx public key: 60e4d65682a829cc8be8882cb4b0f1d64884d0458bd888f4cdc6a9ec3d0b9eb2
Timestamp: 1724319969 Timestamp [UCT]: 2024-08-22 09:46:09 Age [y:d:h:m:s]: 00:139:20:12:55
Block: 1093387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100016 RingCT/type: yes/0
Extra: 0160e4d65682a829cc8be8882cb4b0f1d64884d0458bd888f4cdc6a9ec3d0b9eb202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40f069e94d7d7ac7121ecff1aaa23ad7c8799ad59d6d500b1539ceb37594daea 0.600000000000 1568320 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1093397, "vin": [ { "gen": { "height": 1093387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40f069e94d7d7ac7121ecff1aaa23ad7c8799ad59d6d500b1539ceb37594daea" } } ], "extra": [ 1, 96, 228, 214, 86, 130, 168, 41, 204, 139, 232, 136, 44, 180, 176, 241, 214, 72, 132, 208, 69, 139, 216, 136, 244, 205, 198, 169, 236, 61, 11, 158, 178, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8