Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 149d590cede84e0be783152111f31b3fee67678c2ee674b54a54fb415dcf6915

Tx prefix hash: 4b451a534b544dd6246083cddd81743641724a6970eb6f3f31e7de5f4b0faa6f
Tx public key: 8906871a97af042c3eada6c9a93631004f6e93b55c09af2010c4724f9f59f3be
Timestamp: 1744040618 Timestamp [UCT]: 2025-04-07 15:43:38 Age [y:d:h:m:s]: 00:222:10:44:32
Block: 1256361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156718 RingCT/type: yes/0
Extra: 018906871a97af042c3eada6c9a93631004f6e93b55c09af2010c4724f9f59f3be021100000009dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9b6e3f05349e18f49306ae59034af7c682860acb9f031fde33a77f366ac3a3f 0.600000000000 1743474 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": 1256371, "vin": [ { "gen": { "height": 1256361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9b6e3f05349e18f49306ae59034af7c682860acb9f031fde33a77f366ac3a3f" } } ], "extra": [ 1, 137, 6, 135, 26, 151, 175, 4, 44, 62, 173, 166, 201, 169, 54, 49, 0, 79, 110, 147, 181, 92, 9, 175, 32, 16, 196, 114, 79, 159, 89, 243, 190, 2, 17, 0, 0, 0, 9, 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