Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a046179beb8ac3840408f4bf2416c1d7b35aaa9adc93b5037ad1dbfbd187da0b

Tx prefix hash: 951c648bfab535e331d6ef73a3f6accd59f64e78fe69e5c08d2af4924ffd6d03
Tx public key: 8ce422e50ee72b81b89dc3dca1d713dfe05c1eaf5187218d842a6589a4214a0d
Timestamp: 1716115960 Timestamp [UCT]: 2024-05-19 10:52:40 Age [y:d:h:m:s]: 01:006:00:45:41
Block: 1025367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265219 RingCT/type: yes/0
Extra: 018ce422e50ee72b81b89dc3dca1d713dfe05c1eaf5187218d842a6589a4214a0d021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b633660491f3a36c4ff707c0b7f28c8cfb1c08d044648e2956c9f4c6dc61b3ea 0.600000000000 1491816 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": 1025377, "vin": [ { "gen": { "height": 1025367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b633660491f3a36c4ff707c0b7f28c8cfb1c08d044648e2956c9f4c6dc61b3ea" } } ], "extra": [ 1, 140, 228, 34, 229, 14, 231, 43, 129, 184, 157, 195, 220, 161, 215, 19, 223, 224, 92, 30, 175, 81, 135, 33, 141, 132, 42, 101, 137, 164, 33, 74, 13, 2, 17, 0, 0, 0, 1, 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