Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 672b0f3ed1e842f7ff9b04d7b78a0eb15c29a22bd2fef3a104ab7c6feaad1ee3

Tx prefix hash: be5eedebbc0228f9aa78da7ce7b9d1cd8fc51777fac775bc9f2b33b62ddda3e2
Tx public key: b5059334ca81659383b6c9db1400d0920f6251396054a1e5b3190d9c63b4d950
Timestamp: 1734111929 Timestamp [UCT]: 2024-12-13 17:45:29 Age [y:d:h:m:s]: 00:101:15:34:20
Block: 1174463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72413 RingCT/type: yes/0
Extra: 01b5059334ca81659383b6c9db1400d0920f6251396054a1e5b3190d9c63b4d9500211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c8a1f3afa051e48a4cf18eaf444056a52e9d177645b8df6711ba1ab5098ab37 0.600000000000 1660618 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": 1174473, "vin": [ { "gen": { "height": 1174463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c8a1f3afa051e48a4cf18eaf444056a52e9d177645b8df6711ba1ab5098ab37" } } ], "extra": [ 1, 181, 5, 147, 52, 202, 129, 101, 147, 131, 182, 201, 219, 20, 0, 208, 146, 15, 98, 81, 57, 96, 84, 161, 229, 179, 25, 13, 156, 99, 180, 217, 80, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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