Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d09a58ae922015dafcfc4f6d29977999fc7a62ae2341728126ccaca153d5b22

Tx prefix hash: ab0a750b1c536e5057d6d8a7b681fcd5132ee9c080f284155b732ce60937acb9
Tx public key: 4a9a51861331c3e0b0a906e39ce821a01c59309de86537483f307995f9ccb5a8
Timestamp: 1716179905 Timestamp [UCT]: 2024-05-20 04:38:25 Age [y:d:h:m:s]: 01:029:12:37:32
Block: 1025890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281903 RingCT/type: yes/0
Extra: 014a9a51861331c3e0b0a906e39ce821a01c59309de86537483f307995f9ccb5a80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83cf25d69ebf6813f007e291613c2cc4d0b108a572786ecfef92f11151a205f6 0.600000000000 1492669 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": 1025900, "vin": [ { "gen": { "height": 1025890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83cf25d69ebf6813f007e291613c2cc4d0b108a572786ecfef92f11151a205f6" } } ], "extra": [ 1, 74, 154, 81, 134, 19, 49, 195, 224, 176, 169, 6, 227, 156, 232, 33, 160, 28, 89, 48, 157, 232, 101, 55, 72, 63, 48, 121, 149, 249, 204, 181, 168, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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