Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37e68d31186179f8d355554a9ddede05b68322c2f1a5cb4c6d1530d770629697

Tx prefix hash: 1af2c99642d33079dfe3c7ca0103e0a32af2bb4ad164c09b34a8307a5c504538
Tx public key: 658d8664c65fb1feed92866ceb39ed490a8df2b10ba42a5141e6b9d092fb2a5a
Timestamp: 1701734613 Timestamp [UCT]: 2023-12-05 00:03:33 Age [y:d:h:m:s]: 00:346:01:33:07
Block: 906118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247799 RingCT/type: yes/0
Extra: 01658d8664c65fb1feed92866ceb39ed490a8df2b10ba42a5141e6b9d092fb2a5a02110000000233af99f4000000000000000000

1 output(s) for total of 0.610456740000 dcy

stealth address amount amount idx
00: a4840abbfa34d131338fa6af7bd20bba31f83939644a68c32afded3aed19f7e0 0.610456740000 1363039 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": 906128, "vin": [ { "gen": { "height": 906118 } } ], "vout": [ { "amount": 610456740, "target": { "key": "a4840abbfa34d131338fa6af7bd20bba31f83939644a68c32afded3aed19f7e0" } } ], "extra": [ 1, 101, 141, 134, 100, 198, 95, 177, 254, 237, 146, 134, 108, 235, 57, 237, 73, 10, 141, 242, 177, 11, 164, 42, 81, 65, 230, 185, 208, 146, 251, 42, 90, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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