Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da435425fec51d27f523161cac531e3eab0cd4abfde2bc87037fa0da180c0784

Tx prefix hash: dcce2ed08db614ca5f16810a51b075050046b1a29377a2b0a2768c7b66af6d87
Tx public key: 60692bfea9e5900a4684df0dd48aef064b531b5aa77e286b2ffc43f6f16be530
Timestamp: 1737664184 Timestamp [UCT]: 2025-01-23 20:29:44 Age [y:d:h:m:s]: 00:300:11:53:19
Block: 1203798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212316 RingCT/type: yes/0
Extra: 0160692bfea9e5900a4684df0dd48aef064b531b5aa77e286b2ffc43f6f16be530021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b407f111a1e51e9e4be4088d881ec46dcbd8384c64a1328c0e7e8a86375bca57 0.600000000000 1690477 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": 1203808, "vin": [ { "gen": { "height": 1203798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b407f111a1e51e9e4be4088d881ec46dcbd8384c64a1328c0e7e8a86375bca57" } } ], "extra": [ 1, 96, 105, 43, 254, 169, 229, 144, 10, 70, 132, 223, 13, 212, 138, 239, 6, 75, 83, 27, 90, 167, 126, 40, 107, 47, 252, 67, 246, 241, 107, 229, 48, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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