Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b813487582138618416f0d6b25f489f4a5bd86dac305a74f803f7e3706b222b4

Tx prefix hash: 89fee8ee63f0ea3f6df2a191c28cec7a7b08173087b0b095e287d87908557da7
Tx public key: dd34b9510cc68e1891fea423db40450705d72cf2781a2680bf2ee37879c0c1c9
Timestamp: 1715676336 Timestamp [UCT]: 2024-05-14 08:45:36 Age [y:d:h:m:s]: 00:337:13:39:32
Block: 1021712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241288 RingCT/type: yes/0
Extra: 01dd34b9510cc68e1891fea423db40450705d72cf2781a2680bf2ee37879c0c1c9021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89588c2320c7d52adebbe4a0c2ee241864e1d0cd65d4a632b0af9c4a4c690075 0.600000000000 1486109 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": 1021722, "vin": [ { "gen": { "height": 1021712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89588c2320c7d52adebbe4a0c2ee241864e1d0cd65d4a632b0af9c4a4c690075" } } ], "extra": [ 1, 221, 52, 185, 81, 12, 198, 142, 24, 145, 254, 164, 35, 219, 64, 69, 7, 5, 215, 44, 242, 120, 26, 38, 128, 191, 46, 227, 120, 121, 192, 193, 201, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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