Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551ca070d4756d8ba54f06735f7a05a63e520d727b70c5ffa67e13f8426101ab

Tx prefix hash: 3a56741fa5d1dbfb7eaa2f69f1915d8f3499eae689e439b9f1e83bc7ba17937d
Tx public key: d1fe04c3018cfd10f17810bd2343d394f7f15159f6e559edc4d7fe0f053bf9b6
Timestamp: 1747452988 Timestamp [UCT]: 2025-05-17 03:36:28 Age [y:d:h:m:s]: 00:180:08:45:26
Block: 1284624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126602 RingCT/type: yes/0
Extra: 01d1fe04c3018cfd10f17810bd2343d394f7f15159f6e559edc4d7fe0f053bf9b60211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee334e54d90c17452af8d94618020dbbea15ac809ad4f1441fb5bbe69dca9dbc 0.600000000000 1772081 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": 1284634, "vin": [ { "gen": { "height": 1284624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee334e54d90c17452af8d94618020dbbea15ac809ad4f1441fb5bbe69dca9dbc" } } ], "extra": [ 1, 209, 254, 4, 195, 1, 140, 253, 16, 241, 120, 16, 189, 35, 67, 211, 148, 247, 241, 81, 89, 246, 229, 89, 237, 196, 215, 254, 15, 5, 59, 249, 182, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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