Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31824dbc0da421eea752657f25e2a8f1ec5c9fc4f20aec065be2a84b2cc3e91b

Tx prefix hash: 28b8055d8f438d1a123c6ce09f1ca2a4f90adbcc74ca4fe770c8559ed7a774b1
Tx public key: 4109de1fc2d813ed30cf9dcc5e83dce2e12401dd44569a48c04e9adca694f7fb
Timestamp: 1580571346 Timestamp [UCT]: 2020-02-01 15:35:46 Age [y:d:h:m:s]: 04:336:01:30:26
Block: 56729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131283 RingCT/type: yes/0
Extra: 014109de1fc2d813ed30cf9dcc5e83dce2e12401dd44569a48c04e9adca694f7fb0211000000034943cd9f000000000000000000

1 output(s) for total of 398.158437482000 dcy

stealth address amount amount idx
00: fbb46f3f5230278f455d1b31c73864dff396ef0c57acde3c2990c7ba952e76b1 398.158437482000 104536 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": 56739, "vin": [ { "gen": { "height": 56729 } } ], "vout": [ { "amount": 398158437482, "target": { "key": "fbb46f3f5230278f455d1b31c73864dff396ef0c57acde3c2990c7ba952e76b1" } } ], "extra": [ 1, 65, 9, 222, 31, 194, 216, 19, 237, 48, 207, 157, 204, 94, 131, 220, 226, 225, 36, 1, 221, 68, 86, 154, 72, 192, 78, 154, 220, 166, 148, 247, 251, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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