Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d898b45f731ea5013bbf705a52365af010bcf4fa882adaed910156e7e0beeb8

Tx prefix hash: 73a7715c52b4e36715fd88fee8b3a9d45d22dfe7f5715194d16e30f77281fbbe
Tx public key: 8a557dc301e9a405bb5fe064f180b4a4e62590b6cfb766683a44fa00fc61a5a6
Timestamp: 1748705892 Timestamp [UCT]: 2025-05-31 15:38:12 Age [y:d:h:m:s]: 00:212:21:53:54
Block: 1295014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149892 RingCT/type: yes/0
Extra: 018a557dc301e9a405bb5fe064f180b4a4e62590b6cfb766683a44fa00fc61a5a6021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ce2a522ee75bf58dd1107b0424dfcb51b0c6c005d2ee8fd794e993a074a1ef3 0.600000000000 1782511 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": 1295024, "vin": [ { "gen": { "height": 1295014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ce2a522ee75bf58dd1107b0424dfcb51b0c6c005d2ee8fd794e993a074a1ef3" } } ], "extra": [ 1, 138, 85, 125, 195, 1, 233, 164, 5, 187, 95, 224, 100, 241, 128, 180, 164, 230, 37, 144, 182, 207, 183, 102, 104, 58, 68, 250, 0, 252, 97, 165, 166, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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