Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4b9826aee2e0f25006b1a910d91605579619ffa6e143473e6c2233a1a14b9cc

Tx prefix hash: 53c187f4553a79570608ab665e66fc372b26addaa34421d6aa8ee72644847334
Tx public key: 741ab16c9ca2a1d4e903767a79b25f2547e7d78a37f75f3e32a460cd9db5d3a4
Timestamp: 1716352064 Timestamp [UCT]: 2024-05-22 04:27:44 Age [y:d:h:m:s]: 00:282:01:19:08
Block: 1027320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201562 RingCT/type: yes/0
Extra: 01741ab16c9ca2a1d4e903767a79b25f2547e7d78a37f75f3e32a460cd9db5d3a402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f90a782dbd4645e9119a449eb4ee626e18649bd5da8b8a6b178ec733cd86ed1e 0.600000000000 1494875 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": 1027330, "vin": [ { "gen": { "height": 1027320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f90a782dbd4645e9119a449eb4ee626e18649bd5da8b8a6b178ec733cd86ed1e" } } ], "extra": [ 1, 116, 26, 177, 108, 156, 162, 161, 212, 233, 3, 118, 122, 121, 178, 95, 37, 71, 231, 215, 138, 55, 247, 95, 62, 50, 164, 96, 205, 157, 181, 211, 164, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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