Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf5547abef82cdecfb59a836090a3f9a71b721aba8fe1cacff3bc421ba18796

Tx prefix hash: f55ce6ba4f499289420a25e4751e0f6a1795ca91a016499ebe28bd77f259d5f4
Tx public key: e5d951886edc07d8d01a86c6aed49fe9b99d20386ca454d8c0bf233cb5c77e70
Timestamp: 1674107456 Timestamp [UCT]: 2023-01-19 05:50:56 Age [y:d:h:m:s]: 02:119:02:11:12
Block: 677949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 606801 RingCT/type: yes/0
Extra: 01e5d951886edc07d8d01a86c6aed49fe9b99d20386ca454d8c0bf233cb5c77e7002110000000352542ceb000000000000000000

1 output(s) for total of 3.480755184000 dcy

stealth address amount amount idx
00: e1cc189f4b36a3f6fb2f93ae02cb011f14d2c734c652e4758752d8ca643236bb 3.480755184000 1119750 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": 677959, "vin": [ { "gen": { "height": 677949 } } ], "vout": [ { "amount": 3480755184, "target": { "key": "e1cc189f4b36a3f6fb2f93ae02cb011f14d2c734c652e4758752d8ca643236bb" } } ], "extra": [ 1, 229, 217, 81, 136, 110, 220, 7, 216, 208, 26, 134, 198, 174, 212, 159, 233, 185, 157, 32, 56, 108, 164, 84, 216, 192, 191, 35, 60, 181, 199, 126, 112, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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