Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54da07569a6a1700badfa820a2261b336fa905dc08409301b2c9234685e624fa

Tx prefix hash: 7a16f29ad0c7c19a6d71ecf1ece7e971d91df97ec3617725d91473cd56cccc8a
Tx public key: b8942572e5f39afbcb8790650501c4cc32346ca931ee7d81dfdbcaeb6bc5bfa2
Timestamp: 1725230294 Timestamp [UCT]: 2024-09-01 22:38:14 Age [y:d:h:m:s]: 00:118:18:17:51
Block: 1100917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84938 RingCT/type: yes/0
Extra: 01b8942572e5f39afbcb8790650501c4cc32346ca931ee7d81dfdbcaeb6bc5bfa2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7970b66085f4b4c6fca20277680257b895c7a5de4b43a87a9b096a9d6d6233 0.600000000000 1576898 of 15

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": 1100927, "vin": [ { "gen": { "height": 1100917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7970b66085f4b4c6fca20277680257b895c7a5de4b43a87a9b096a9d6d6233" } } ], "extra": [ 1, 184, 148, 37, 114, 229, 243, 154, 251, 203, 135, 144, 101, 5, 1, 196, 204, 50, 52, 108, 169, 49, 238, 125, 129, 223, 219, 202, 235, 107, 197, 191, 162, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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