Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510f8a3a917efce22ef00aa159699deb47d491a6cec5226cb17868519421bf11

Tx prefix hash: 2218c64e03d25cfbe93b5fac193a49a8c0db16d0c7f530eef33c2b6fca4f12af
Tx public key: e41ab53179c4f1971d109c1b06fb78a26350a7d4fe0f4e8ebb9d409f86ad8ebd
Timestamp: 1711732722 Timestamp [UCT]: 2024-03-29 17:18:42 Age [y:d:h:m:s]: 01:018:05:40:31
Block: 989031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273984 RingCT/type: yes/0
Extra: 01e41ab53179c4f1971d109c1b06fb78a26350a7d4fe0f4e8ebb9d409f86ad8ebd0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5231fec700ab20a15e69d4bf80bdc7559733e24fe3fbdaf71d30d27c8d1b60d1 0.600000000000 1449324 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": 989041, "vin": [ { "gen": { "height": 989031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5231fec700ab20a15e69d4bf80bdc7559733e24fe3fbdaf71d30d27c8d1b60d1" } } ], "extra": [ 1, 228, 26, 181, 49, 121, 196, 241, 151, 29, 16, 156, 27, 6, 251, 120, 162, 99, 80, 167, 212, 254, 15, 78, 142, 187, 157, 64, 159, 134, 173, 142, 189, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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