Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a98e99cadd051fc7a247f51c7c1349097ffedc94c00b2ecf30fb8594b9364aa0

Tx prefix hash: 0cd4e90c2e1cc0a803cee48365adeec04efad7e3b4d1374d9519354f74e2d5c1
Tx public key: 2b9462126753fe133a4d3f0251d23d5e823dcf14b22e67078d55e7315ba044f1
Timestamp: 1705864197 Timestamp [UCT]: 2024-01-21 19:09:57 Age [y:d:h:m:s]: 01:098:16:18:11
Block: 940333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331656 RingCT/type: yes/0
Extra: 012b9462126753fe133a4d3f0251d23d5e823dcf14b22e67078d55e7315ba044f102110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb86ffbef590708efcb45b9e2332ed7db0c26b1546f4044c6024a6176b7c358f 0.600000000000 1398469 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": 940343, "vin": [ { "gen": { "height": 940333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb86ffbef590708efcb45b9e2332ed7db0c26b1546f4044c6024a6176b7c358f" } } ], "extra": [ 1, 43, 148, 98, 18, 103, 83, 254, 19, 58, 77, 63, 2, 81, 210, 61, 94, 130, 61, 207, 20, 178, 46, 103, 7, 141, 85, 231, 49, 91, 160, 68, 241, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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