Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 870cf1935eb4d0c9f4b20d591f828301ba8c726406941415dc620de8cf649023

Tx prefix hash: 2bda1dff907f01716884c2390a09b68f0b6a6f213616f4a2dc62c2ed78c823fe
Tx public key: 41748df7c9fe182b7c01171822e08ea167948ca182d00f53cc64e8b82bc26ef6
Timestamp: 1698505423 Timestamp [UCT]: 2023-10-28 15:03:43 Age [y:d:h:m:s]: 01:204:08:08:10
Block: 879565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407065 RingCT/type: yes/0
Extra: 0141748df7c9fe182b7c01171822e08ea167948ca182d00f53cc64e8b82bc26ef602110000000233af99f4000000000000000000

1 output(s) for total of 0.747542767000 dcy

stealth address amount amount idx
00: a6bdf60ffe14b27133a8a16b36c5415d9d88b9b58882f34e4eae0b1c64b78b97 0.747542767000 1335097 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": 879575, "vin": [ { "gen": { "height": 879565 } } ], "vout": [ { "amount": 747542767, "target": { "key": "a6bdf60ffe14b27133a8a16b36c5415d9d88b9b58882f34e4eae0b1c64b78b97" } } ], "extra": [ 1, 65, 116, 141, 247, 201, 254, 24, 43, 124, 1, 23, 24, 34, 224, 142, 161, 103, 148, 140, 161, 130, 208, 15, 83, 204, 100, 232, 184, 43, 194, 110, 246, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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