Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cec2a66a23129287b39b2e6444257c45f7c97195d4d36ccf23ca299e213bfa6

Tx prefix hash: 8492ba7f0559595c75c30ea11583336303b264bcf27e88999401a2366a480fc0
Tx public key: 3f47349c004158f96fbd710e3724cd575a078a99f77979c3f9cb3b2df7d0f57b
Timestamp: 1756613452 Timestamp [UCT]: 2025-08-31 04:10:52 Age [y:d:h:m:s]: 00:115:00:27:12
Block: 1358137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82202 RingCT/type: yes/0
Extra: 013f47349c004158f96fbd710e3724cd575a078a99f77979c3f9cb3b2df7d0f57b021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7bf2f8abd38f8e62d77fcbf927d8d20b6a3381defddc2e19347da779565ee97 0.600000000000 1846148 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": 1358147, "vin": [ { "gen": { "height": 1358137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7bf2f8abd38f8e62d77fcbf927d8d20b6a3381defddc2e19347da779565ee97" } } ], "extra": [ 1, 63, 71, 52, 156, 0, 65, 88, 249, 111, 189, 113, 14, 55, 36, 205, 87, 90, 7, 138, 153, 247, 121, 121, 195, 249, 203, 59, 45, 247, 208, 245, 123, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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