Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc66b8fe29d129ec551998df88862a48c6e9c78f225df6d986ad771612fb78e3

Tx prefix hash: 287eaf0ca2e4f252811ee84195a8616a04a40a81380746d383f56454398c924f
Tx public key: fcf2a17b29776055d1cfe3c84d21b08d052394231a5d5558f2b913910dc468c6
Timestamp: 1695918689 Timestamp [UCT]: 2023-09-28 16:31:29 Age [y:d:h:m:s]: 01:239:07:55:09
Block: 858113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432144 RingCT/type: yes/0
Extra: 01fcf2a17b29776055d1cfe3c84d21b08d052394231a5d5558f2b913910dc468c602110000000375e3f0e9000000000000000000

1 output(s) for total of 0.880471811000 dcy

stealth address amount amount idx
00: 5a850a2d0a87fd0b2a32538f1d5eaad0f90b8d7deaa02333ac0b1c4cbe8e6efd 0.880471811000 1312277 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": 858123, "vin": [ { "gen": { "height": 858113 } } ], "vout": [ { "amount": 880471811, "target": { "key": "5a850a2d0a87fd0b2a32538f1d5eaad0f90b8d7deaa02333ac0b1c4cbe8e6efd" } } ], "extra": [ 1, 252, 242, 161, 123, 41, 119, 96, 85, 209, 207, 227, 200, 77, 33, 176, 141, 5, 35, 148, 35, 26, 93, 85, 88, 242, 185, 19, 145, 13, 196, 104, 198, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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