Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3815471860050d4bce53ec18e14130edbb99de05cfe1e05f8c9f13675369b891

Tx prefix hash: 71d0ec826d0591c0f4e1ac5c4b11d645dadf677b8786e51bc7570479cf6e988d
Tx public key: 20c1217c5dd0db05a1d3569dc6f36a92f1cfb2fb78ce4a456cb0e961976b09d7
Timestamp: 1716591747 Timestamp [UCT]: 2024-05-24 23:02:27 Age [y:d:h:m:s]: 00:160:01:51:02
Block: 1029301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114585 RingCT/type: yes/0
Extra: 0120c1217c5dd0db05a1d3569dc6f36a92f1cfb2fb78ce4a456cb0e961976b09d702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ba48bc6cdf17e53731e0ef9952bcdb75a0ede9048fd195d8dca045fca63cbfb 0.600000000000 1497352 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": 1029311, "vin": [ { "gen": { "height": 1029301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ba48bc6cdf17e53731e0ef9952bcdb75a0ede9048fd195d8dca045fca63cbfb" } } ], "extra": [ 1, 32, 193, 33, 124, 93, 208, 219, 5, 161, 211, 86, 157, 198, 243, 106, 146, 241, 207, 178, 251, 120, 206, 74, 69, 108, 176, 233, 97, 151, 107, 9, 215, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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