Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc244991a3550753520c86d3babc7206f88317ae41f025beb4f239ad5e30c78

Tx prefix hash: b44f23b86ff99d540a7715cb2b0928927a80a34ee21e17db5232339d5c996c5c
Tx public key: cc07ea30ca7e40bd1c3a0bec43f71d8ab601ec08f55c377d0737a92eca8b257e
Timestamp: 1668891570 Timestamp [UCT]: 2022-11-19 20:59:30 Age [y:d:h:m:s]: 02:052:21:30:12
Block: 634756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559733 RingCT/type: yes/0
Extra: 01cc07ea30ca7e40bd1c3a0bec43f71d8ab601ec08f55c377d0737a92eca8b257e02110000000183600029000000000000000000

1 output(s) for total of 4.839381736000 dcy

stealth address amount amount idx
00: e6cbe9d101fdc37c411299da42c792862902011a4ad9b7288c284fa3b4942826 4.839381736000 1073937 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": 634766, "vin": [ { "gen": { "height": 634756 } } ], "vout": [ { "amount": 4839381736, "target": { "key": "e6cbe9d101fdc37c411299da42c792862902011a4ad9b7288c284fa3b4942826" } } ], "extra": [ 1, 204, 7, 234, 48, 202, 126, 64, 189, 28, 58, 11, 236, 67, 247, 29, 138, 182, 1, 236, 8, 245, 92, 55, 125, 7, 55, 169, 46, 202, 139, 37, 126, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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