Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e20e1efee44e5e351fea98310216e1f2aa3da6781c1f506a0471a48324c7dbe

Tx prefix hash: 6be93d8bba71510bdb6b7a576ee63160d0691c9c2609608fa0fa95b766df40d0
Tx public key: 0bae5afb50aba0b5e9f6774fd29e43bd8861dadd82d15d1c4a42f364d998c71d
Timestamp: 1740793469 Timestamp [UCT]: 2025-03-01 01:44:29 Age [y:d:h:m:s]: 00:265:21:46:35
Block: 1229469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187811 RingCT/type: yes/0
Extra: 010bae5afb50aba0b5e9f6774fd29e43bd8861dadd82d15d1c4a42f364d998c71d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c2dba18d062383625e9677cdd43fe3838d060acc73fc8163caf54a1fc7cd27 0.600000000000 1716356 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": 1229479, "vin": [ { "gen": { "height": 1229469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c2dba18d062383625e9677cdd43fe3838d060acc73fc8163caf54a1fc7cd27" } } ], "extra": [ 1, 11, 174, 90, 251, 80, 171, 160, 181, 233, 246, 119, 79, 210, 158, 67, 189, 136, 97, 218, 221, 130, 209, 93, 28, 74, 66, 243, 100, 217, 152, 199, 29, 2, 17, 0, 0, 0, 5, 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