Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fcc4446e5e2d96bb9c35bb33035f9e79d884faad3dc5d8a12610c4de7077db3

Tx prefix hash: 9c51c3dd1582fc0ea5a92429fadcf31fc1ffa5d42af9ca9a7e51ab47e211d967
Tx public key: b5a445d1f9f36e91890655eb85eca5d2091b70b750de9d18fcb645ac8c5e9a92
Timestamp: 1745667272 Timestamp [UCT]: 2025-04-26 11:34:32 Age [y:d:h:m:s]: 00:015:07:30:39
Block: 1269842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10940 RingCT/type: yes/0
Extra: 01b5a445d1f9f36e91890655eb85eca5d2091b70b750de9d18fcb645ac8c5e9a9202110000000edbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b7e82e0a0461f04d80819432ac9e01d87e6f5315526bd1d29dea4490288adba 0.600000000000 1757081 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": 1269852, "vin": [ { "gen": { "height": 1269842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b7e82e0a0461f04d80819432ac9e01d87e6f5315526bd1d29dea4490288adba" } } ], "extra": [ 1, 181, 164, 69, 209, 249, 243, 110, 145, 137, 6, 85, 235, 133, 236, 165, 210, 9, 27, 112, 183, 80, 222, 157, 24, 252, 182, 69, 172, 140, 94, 154, 146, 2, 17, 0, 0, 0, 14, 219, 181, 113, 193, 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