Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a9634a631b3748596365408e71497089fa13247f3650967031d21ffe75fe77a

Tx prefix hash: 28e907e0b15da758ee6f10fa48e40bb0f4daa979a927cd6504f4c4bc88650617
Tx public key: bd960d074e4bbba92b81a3b44b61d6a7ae59b6cf93d514b5f1928715a166f209
Timestamp: 1749492287 Timestamp [UCT]: 2025-06-09 18:04:47 Age [y:d:h:m:s]: 00:163:13:56:42
Block: 1301511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114594 RingCT/type: yes/0
Extra: 01bd960d074e4bbba92b81a3b44b61d6a7ae59b6cf93d514b5f1928715a166f209021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa538ebfe5e346f5a5ad698bb31f3f80d8a6dec3ba30219106ddea8e4d9f5827 0.600000000000 1789070 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": 1301521, "vin": [ { "gen": { "height": 1301511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa538ebfe5e346f5a5ad698bb31f3f80d8a6dec3ba30219106ddea8e4d9f5827" } } ], "extra": [ 1, 189, 150, 13, 7, 78, 75, 187, 169, 43, 129, 163, 180, 75, 97, 214, 167, 174, 89, 182, 207, 147, 213, 20, 181, 241, 146, 135, 21, 161, 102, 242, 9, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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