Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 894e1d83f58fadb1f49dfac9c6552a16a8c4a8a31e5400cfea587f4c9c6b0ad0

Tx prefix hash: f338747ad059755bb7cf0b2a36adbcb792d0996d626e2557f65c86882442f48d
Tx public key: 734ced6567f89be84d4e3f18ea9f71592831b4ae150e74c6056f16b9c2c5622e
Timestamp: 1634932057 Timestamp [UCT]: 2021-10-22 19:47:37 Age [y:d:h:m:s]: 04:010:03:53:02
Block: 358320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043943 RingCT/type: yes/0
Extra: 01734ced6567f89be84d4e3f18ea9f71592831b4ae150e74c6056f16b9c2c5622e02110000000106faf294000000000000000000

1 output(s) for total of 39.878379841000 dcy

stealth address amount amount idx
00: afd0cf984ace66b0e7b7ea32ca717a06c926e299f684217d7d84a9c32258adf5 39.878379841000 730175 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": 358330, "vin": [ { "gen": { "height": 358320 } } ], "vout": [ { "amount": 39878379841, "target": { "key": "afd0cf984ace66b0e7b7ea32ca717a06c926e299f684217d7d84a9c32258adf5" } } ], "extra": [ 1, 115, 76, 237, 101, 103, 248, 155, 232, 77, 78, 63, 24, 234, 159, 113, 89, 40, 49, 180, 174, 21, 14, 116, 198, 5, 111, 22, 185, 194, 197, 98, 46, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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