Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61fb97538721b5af950a5e5af09e371bf02c375dfd14409e9b1b38f7b2275e4e

Tx prefix hash: aac90997f11b74c3419f9af1d4bc987bbca7944d7ce034274dd858f319f5178d
Tx public key: d6beda6f34e85a0603efc8a647efe0ba1a8e3c44f654dd516dd90c3f9f590285
Timestamp: 1703900688 Timestamp [UCT]: 2023-12-30 01:44:48 Age [y:d:h:m:s]: 01:314:01:11:59
Block: 924081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483283 RingCT/type: yes/0
Extra: 01d6beda6f34e85a0603efc8a647efe0ba1a8e3c44f654dd516dd90c3f9f5902850211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbfbce3c4ee9c93636ea9573e39afdd2da89983557e5b4cfd51ab51a2f35cf39 0.600000000000 1381823 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": 924091, "vin": [ { "gen": { "height": 924081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbfbce3c4ee9c93636ea9573e39afdd2da89983557e5b4cfd51ab51a2f35cf39" } } ], "extra": [ 1, 214, 190, 218, 111, 52, 232, 90, 6, 3, 239, 200, 166, 71, 239, 224, 186, 26, 142, 60, 68, 246, 84, 221, 81, 109, 217, 12, 63, 159, 89, 2, 133, 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