Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86de84766c1363382e056405958615b0e16a5f8da6b21879d8dadf4fbac47940

Tx prefix hash: f03ce490e306702414ab5d71da165069acfeef08862c6d5c4ebbef6931ee71f5
Tx public key: 2f31fbe7ac5a29a318535c4443a1a8d1327831ab539c6d6e8aa2571566fb45ef
Timestamp: 1672892424 Timestamp [UCT]: 2023-01-05 04:20:24 Age [y:d:h:m:s]: 01:332:14:16:54
Block: 667864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498733 RingCT/type: yes/0
Extra: 012f31fbe7ac5a29a318535c4443a1a8d1327831ab539c6d6e8aa2571566fb45ef02110000000252542ceb000000000000000000

1 output(s) for total of 3.759146791000 dcy

stealth address amount amount idx
00: b2bf7fea4f1e0e0cfb916051b8e44afaa10fd0e603c7e59949eeb10ff37f9703 3.759146791000 1109083 of 0

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": 667874, "vin": [ { "gen": { "height": 667864 } } ], "vout": [ { "amount": 3759146791, "target": { "key": "b2bf7fea4f1e0e0cfb916051b8e44afaa10fd0e603c7e59949eeb10ff37f9703" } } ], "extra": [ 1, 47, 49, 251, 231, 172, 90, 41, 163, 24, 83, 92, 68, 67, 161, 168, 209, 50, 120, 49, 171, 83, 156, 109, 110, 138, 162, 87, 21, 102, 251, 69, 239, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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