Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b327412f09be010b6058ccceeacb3b7d4e48f6947ce52fd4af7aee9b08e63537

Tx prefix hash: 39ef274f2ced16a0de7ccc3ddc014e6f63aba6c02848383dccfce21d8de9c969
Tx public key: 372d5985f4da5134a5e4630e8683ecba6f2512bdc41ff834a6c840d6446e7187
Timestamp: 1735423683 Timestamp [UCT]: 2024-12-28 22:08:03 Age [y:d:h:m:s]: 00:163:11:29:00
Block: 1185292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116684 RingCT/type: yes/0
Extra: 01372d5985f4da5134a5e4630e8683ecba6f2512bdc41ff834a6c840d6446e71870211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7809eeb77f6c3e7d7d2f735fe79e74d09b0ae68f95ed19c807c5928bd2fad4d1 0.600000000000 1671759 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": 1185302, "vin": [ { "gen": { "height": 1185292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7809eeb77f6c3e7d7d2f735fe79e74d09b0ae68f95ed19c807c5928bd2fad4d1" } } ], "extra": [ 1, 55, 45, 89, 133, 244, 218, 81, 52, 165, 228, 99, 14, 134, 131, 236, 186, 111, 37, 18, 189, 196, 31, 248, 52, 166, 200, 64, 214, 68, 110, 113, 135, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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