Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8406de4a20c43c0fef797466d98f5aa71b4b34c3cc7c7e27685712a010fb77df

Tx prefix hash: 42c987c8058457f34c690914918ac51c92866f668099aa9c64f9bd86c2d53e36
Tx public key: 018736f2e0a3ff86a529e9d6546145267514fd6d00f05b9190c86978205d39f1
Timestamp: 1726379678 Timestamp [UCT]: 2024-09-15 05:54:38 Age [y:d:h:m:s]: 00:117:09:51:20
Block: 1110443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83960 RingCT/type: yes/0
Extra: 01018736f2e0a3ff86a529e9d6546145267514fd6d00f05b9190c86978205d39f1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e23ed227c66ebeac2a3da9c6a55e797c9559f83b503e4ed62cec37c7151064 0.600000000000 1589052 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": 1110453, "vin": [ { "gen": { "height": 1110443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e23ed227c66ebeac2a3da9c6a55e797c9559f83b503e4ed62cec37c7151064" } } ], "extra": [ 1, 1, 135, 54, 242, 224, 163, 255, 134, 165, 41, 233, 214, 84, 97, 69, 38, 117, 20, 253, 109, 0, 240, 91, 145, 144, 200, 105, 120, 32, 93, 57, 241, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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