Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351c3d536865f3e701445f1bee299fdae116d82321bfe9087610529359cb8f9b

Tx prefix hash: a44752bb13f57ca25028997d0b276bb86cc06314f5615a586dbfda40ee4ea39a
Tx public key: 498de3ffe45d70f7797b30b943752f76f6c0ab65569b5d4a83eb343dc68c0148
Timestamp: 1735889010 Timestamp [UCT]: 2025-01-03 07:23:30 Age [y:d:h:m:s]: 00:163:00:55:20
Block: 1189172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116242 RingCT/type: yes/0
Extra: 01498de3ffe45d70f7797b30b943752f76f6c0ab65569b5d4a83eb343dc68c0148021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7f7868e5c82dadb54bfcbeeabf5f82e032d539247107c6d6cf7b7a5acd4d6a 0.600000000000 1675677 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": 1189182, "vin": [ { "gen": { "height": 1189172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7f7868e5c82dadb54bfcbeeabf5f82e032d539247107c6d6cf7b7a5acd4d6a" } } ], "extra": [ 1, 73, 141, 227, 255, 228, 93, 112, 247, 121, 123, 48, 185, 67, 117, 47, 118, 246, 192, 171, 101, 86, 155, 93, 74, 131, 235, 52, 61, 198, 140, 1, 72, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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