Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27b489ff0b18ee60421e4203b7f70df0ba168b868cebb8e5374c1ae52ba72eb9

Tx prefix hash: 9889981a8ae72d1840f8faad0ef0cee46793a446cf0249fd5295630b0e531582
Tx public key: 7d18b4a9578dcb6d2623a8676efa2831f9f33ce9f094ebdd10e90cd0859c3da6
Timestamp: 1719125063 Timestamp [UCT]: 2024-06-23 06:44:23 Age [y:d:h:m:s]: 00:305:17:23:00
Block: 1050288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218499 RingCT/type: yes/0
Extra: 017d18b4a9578dcb6d2623a8676efa2831f9f33ce9f094ebdd10e90cd0859c3da602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba7967b7d80b01d4cebf6041b3e6f4b5aefd9da02acca92d2ce5884cc8f832d3 0.600000000000 1520451 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": 1050298, "vin": [ { "gen": { "height": 1050288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba7967b7d80b01d4cebf6041b3e6f4b5aefd9da02acca92d2ce5884cc8f832d3" } } ], "extra": [ 1, 125, 24, 180, 169, 87, 141, 203, 109, 38, 35, 168, 103, 110, 250, 40, 49, 249, 243, 60, 233, 240, 148, 235, 221, 16, 233, 12, 208, 133, 156, 61, 166, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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