Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d3bcb6d36b7e2aa6c1bbe939672c62a449a2a0557d2542632d8ca3cb50e454b

Tx prefix hash: ddb6dd0326777e695c1fa42ff79e10afe7e041fb95b85c07668c84da650439f7
Tx public key: 8fc8f9c911e5f06e0103375e890d844124d231a7f5e289b5a6d240a8000d42f6
Timestamp: 1745732299 Timestamp [UCT]: 2025-04-27 05:38:19 Age [y:d:h:m:s]: 00:011:17:23:27
Block: 1270369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8384 RingCT/type: yes/0
Extra: 018fc8f9c911e5f06e0103375e890d844124d231a7f5e289b5a6d240a8000d42f602110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33e15197bb7236af0eb7c3a3beb2af9af811adb73e2d28630763c27487c1ac85 0.600000000000 1757612 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": 1270379, "vin": [ { "gen": { "height": 1270369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33e15197bb7236af0eb7c3a3beb2af9af811adb73e2d28630763c27487c1ac85" } } ], "extra": [ 1, 143, 200, 249, 201, 17, 229, 240, 110, 1, 3, 55, 94, 137, 13, 132, 65, 36, 210, 49, 167, 245, 226, 137, 181, 166, 210, 64, 168, 0, 13, 66, 246, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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