Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea83903ec39bf5b4f90b7991e78bbf747d1dfc61603805a7bbb33dd49b0df38b

Tx prefix hash: ac02ce01c64668e650f55b9d755bc08988b929b8e630cb5aba870f133dc7cbb3
Tx public key: 2d0c7768f89818fa8a56b287754efc6c9696c34bcff8230d1df2cb0d5977f1af
Timestamp: 1730840803 Timestamp [UCT]: 2024-11-05 21:06:43 Age [y:d:h:m:s]: 00:078:16:07:36
Block: 1147332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56257 RingCT/type: yes/0
Extra: 012d0c7768f89818fa8a56b287754efc6c9696c34bcff8230d1df2cb0d5977f1af021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79688f09133ce35fe8d8cebadf40d898c5c641fdcf97546a73fdccec6becea0 0.600000000000 1632027 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": 1147342, "vin": [ { "gen": { "height": 1147332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79688f09133ce35fe8d8cebadf40d898c5c641fdcf97546a73fdccec6becea0" } } ], "extra": [ 1, 45, 12, 119, 104, 248, 152, 24, 250, 138, 86, 178, 135, 117, 78, 252, 108, 150, 150, 195, 75, 207, 248, 35, 13, 29, 242, 203, 13, 89, 119, 241, 175, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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