Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3495ce4d94f9085380d0437ecfac09838e897c3954ea64b3eb38d4ca942daba2

Tx prefix hash: dbd0ae15146560241d96a1855ab9ab78cb2ae3c6a8cb421e12755bcaa27014dc
Tx public key: a978c4d795ba9418e5bf11d709d364e7b5248db3a739a86e54636b286cb49234
Timestamp: 1704469143 Timestamp [UCT]: 2024-01-05 15:39:03 Age [y:d:h:m:s]: 01:132:15:33:08
Block: 928777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355954 RingCT/type: yes/0
Extra: 01a978c4d795ba9418e5bf11d709d364e7b5248db3a739a86e54636b286cb492340211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 556de8a3aa6aa24c71a19f8d24a36a777dae100310f1702a70a33b809d429cd8 0.600000000000 1386639 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": 928787, "vin": [ { "gen": { "height": 928777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556de8a3aa6aa24c71a19f8d24a36a777dae100310f1702a70a33b809d429cd8" } } ], "extra": [ 1, 169, 120, 196, 215, 149, 186, 148, 24, 229, 191, 17, 215, 9, 211, 100, 231, 181, 36, 141, 179, 167, 57, 168, 110, 84, 99, 107, 40, 108, 180, 146, 52, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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