Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a5d4c78dae2992bd8d8e903b95fdf7be63f81d19643f5ce1aa4bfc183eaae99

Tx prefix hash: 12b8eeb91fc571ee6786caa4d25733e911134d3e3527afd4bcfa6061dd7698a9
Tx public key: 398aa8df9a33c384db319ad29395cfa6e938732104e24c1f3695eb0db0ef00bf
Timestamp: 1742809687 Timestamp [UCT]: 2025-03-24 09:48:07 Age [y:d:h:m:s]: 00:049:14:00:31
Block: 1246173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35463 RingCT/type: yes/0
Extra: 01398aa8df9a33c384db319ad29395cfa6e938732104e24c1f3695eb0db0ef00bf021100000008c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32e8459a11b6ae949cd2ba1890fa6e4cd9eb766e1254fa3922ccd03aa2cb678 0.600000000000 1733172 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": 1246183, "vin": [ { "gen": { "height": 1246173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32e8459a11b6ae949cd2ba1890fa6e4cd9eb766e1254fa3922ccd03aa2cb678" } } ], "extra": [ 1, 57, 138, 168, 223, 154, 51, 195, 132, 219, 49, 154, 210, 147, 149, 207, 166, 233, 56, 115, 33, 4, 226, 76, 31, 54, 149, 235, 13, 176, 239, 0, 191, 2, 17, 0, 0, 0, 8, 198, 116, 9, 88, 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