Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ab8dd1f851a57f1d9dfac402fac1b74d8d6b1531a66bdaa6c7cd2ed7617a083

Tx prefix hash: 02c8167f0b50d64d709e2c23feee20a0aba6004174a6ada20a275d90c55ba068
Tx public key: 0ac33625531266a6338281dbe9cb51dc8cdd97a72dd569a02c0ab26b2d72adb0
Timestamp: 1578704502 Timestamp [UCT]: 2020-01-11 01:01:42 Age [y:d:h:m:s]: 05:122:01:25:42
Block: 42997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237290 RingCT/type: yes/0
Extra: 010ac33625531266a6338281dbe9cb51dc8cdd97a72dd569a02c0ab26b2d72adb00211000000088a2ee0d9000000000000000000

1 output(s) for total of 442.113659812000 dcy

stealth address amount amount idx
00: 340f707aaf517ac5c4829cf47d86c0cad286f84bf687351a7ffa4fa3cad2f085 442.113659812000 77669 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": 43007, "vin": [ { "gen": { "height": 42997 } } ], "vout": [ { "amount": 442113659812, "target": { "key": "340f707aaf517ac5c4829cf47d86c0cad286f84bf687351a7ffa4fa3cad2f085" } } ], "extra": [ 1, 10, 195, 54, 37, 83, 18, 102, 166, 51, 130, 129, 219, 233, 203, 81, 220, 140, 221, 151, 167, 45, 213, 105, 160, 44, 10, 178, 107, 45, 114, 173, 176, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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