Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d69a7271484dbeb4ce64efe5f910d0097e9ad9fb695f462f622e27f2f17510cf

Tx prefix hash: 34a3e0fd5f1a4dc916fc285d53059031045a6e23a7b423c51d62943a22a5fdfc
Tx public key: e65464691a7a160e5c7980b883dca7fa1762a7639a4ac8f38d9a9195aad8170e
Timestamp: 1580589496 Timestamp [UCT]: 2020-02-01 20:38:16 Age [y:d:h:m:s]: 05:121:15:01:28
Block: 56751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1238850 RingCT/type: yes/0
Extra: 01e65464691a7a160e5c7980b883dca7fa1762a7639a4ac8f38d9a9195aad8170e02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 398.071606622000 dcy

stealth address amount amount idx
00: deb2574bef1132a0914c5d714d3ec6b2571a491ae5fa6799b2d08f9fe5cd7be2 398.071606622000 104632 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": 56761, "vin": [ { "gen": { "height": 56751 } } ], "vout": [ { "amount": 398071606622, "target": { "key": "deb2574bef1132a0914c5d714d3ec6b2571a491ae5fa6799b2d08f9fe5cd7be2" } } ], "extra": [ 1, 230, 84, 100, 105, 26, 122, 22, 14, 92, 121, 128, 184, 131, 220, 167, 250, 23, 98, 167, 99, 154, 74, 200, 243, 141, 154, 145, 149, 170, 216, 23, 14, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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