Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 234a55c4b6f06fc8c7f074d82ce073993de3d1a71092fd48c4096487c349ce5e

Tx prefix hash: 23f139ed93ad9392c4b2a150e09c59b3fde547d49cabb4c6797f31dfa70fde83
Tx public key: ddfbfd95f6c5607488a563a89c2462c3c35d5279b05803e950852c5354d89efe
Timestamp: 1741278924 Timestamp [UCT]: 2025-03-06 16:35:24 Age [y:d:h:m:s]: 00:006:00:52:25
Block: 1233507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4328 RingCT/type: yes/0
Extra: 01ddfbfd95f6c5607488a563a89c2462c3c35d5279b05803e950852c5354d89efe021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11259aae52e3553b3b1f42f6c3738f6c257f71fd7a9098c526331dd4e0f34359 0.600000000000 1720428 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": 1233517, "vin": [ { "gen": { "height": 1233507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11259aae52e3553b3b1f42f6c3738f6c257f71fd7a9098c526331dd4e0f34359" } } ], "extra": [ 1, 221, 251, 253, 149, 246, 197, 96, 116, 136, 165, 99, 168, 156, 36, 98, 195, 195, 93, 82, 121, 176, 88, 3, 233, 80, 133, 44, 83, 84, 216, 158, 254, 2, 17, 0, 0, 0, 3, 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