Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f989a290203834dd25c5ef4f394b66ba9330ebda5f80151f84e3bfa6b28826e6

Tx prefix hash: d210ef9daa38feaa1dd6f4756debdf2d7c8b00055f6c2902f0ca2fc977052506
Tx public key: 8bf1bfc70310bf1c2825ac59a2b5221b4d62e85d35e7f286da07fedb07c3e051
Timestamp: 1731514320 Timestamp [UCT]: 2024-11-13 16:12:00 Age [y:d:h:m:s]: 00:362:15:58:51
Block: 1152924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256741 RingCT/type: yes/0
Extra: 018bf1bfc70310bf1c2825ac59a2b5221b4d62e85d35e7f286da07fedb07c3e0510211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2886b2c2caa45b52e1685c7f59bf041dc605aa99c03b0e2ec5e167e7414ff8c 0.600000000000 1638531 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": 1152934, "vin": [ { "gen": { "height": 1152924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2886b2c2caa45b52e1685c7f59bf041dc605aa99c03b0e2ec5e167e7414ff8c" } } ], "extra": [ 1, 139, 241, 191, 199, 3, 16, 191, 28, 40, 37, 172, 89, 162, 181, 34, 27, 77, 98, 232, 93, 53, 231, 242, 134, 218, 7, 254, 219, 7, 195, 224, 81, 2, 17, 0, 0, 0, 2, 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