Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 844b420e478de61b719a985441c32195f7ec1d4d370b8b0390bb4541e129123b

Tx prefix hash: 4209e04e69c0d2443f84c28695304815a76f29db070a41c8b3a67e514ae0a488
Tx public key: 1107862ad8a8ac56097246d19011f182e4bca0264c9a949f82ab65bf24b226c5
Timestamp: 1698892698 Timestamp [UCT]: 2023-11-02 02:38:18 Age [y:d:h:m:s]: 01:157:11:26:12
Block: 882769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373547 RingCT/type: yes/0
Extra: 011107862ad8a8ac56097246d19011f182e4bca0264c9a949f82ab65bf24b226c502110000001375e3f0e9000000000000000000

1 output(s) for total of 0.729490863000 dcy

stealth address amount amount idx
00: 3a22f14b56bb516c9dc473d856bbc0e9fbdd00138769b1c883c4b76aff187f76 0.729490863000 1338447 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": 882779, "vin": [ { "gen": { "height": 882769 } } ], "vout": [ { "amount": 729490863, "target": { "key": "3a22f14b56bb516c9dc473d856bbc0e9fbdd00138769b1c883c4b76aff187f76" } } ], "extra": [ 1, 17, 7, 134, 42, 216, 168, 172, 86, 9, 114, 70, 209, 144, 17, 241, 130, 228, 188, 160, 38, 76, 154, 148, 159, 130, 171, 101, 191, 36, 178, 38, 197, 2, 17, 0, 0, 0, 19, 117, 227, 240, 233, 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