Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5daa5f7fecd987601e6c94a82616dcfe374e442c361cf26f8a91af2a09afb4

Tx prefix hash: 886b2d47969ea6074aeab377300a257262c4dcd654e69894007b8b7fe339b8a9
Tx public key: 0e1175d1e2ceeceb945b8ba4525cf8f0a3a28d682d3fbfdd394ce239a199ed99
Timestamp: 1574656133 Timestamp [UCT]: 2019-11-25 04:28:53 Age [y:d:h:m:s]: 05:101:00:54:53
Block: 16907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214826 RingCT/type: yes/0
Extra: 010e1175d1e2ceeceb945b8ba4525cf8f0a3a28d682d3fbfdd394ce239a199ed9902110000000229332f00000000000000000000

1 output(s) for total of 539.486985052000 dcy

stealth address amount amount idx
00: 1020a1c7c1fc43fe7aaf1a7df963343e7fe043e104334540d081fc77130e4394 539.486985052000 24051 of 0

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": 16917, "vin": [ { "gen": { "height": 16907 } } ], "vout": [ { "amount": 539486985052, "target": { "key": "1020a1c7c1fc43fe7aaf1a7df963343e7fe043e104334540d081fc77130e4394" } } ], "extra": [ 1, 14, 17, 117, 209, 226, 206, 236, 235, 148, 91, 139, 164, 82, 92, 248, 240, 163, 162, 141, 104, 45, 63, 191, 221, 57, 76, 226, 57, 161, 153, 237, 153, 2, 17, 0, 0, 0, 2, 41, 51, 47, 0, 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