Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d099a533d30f5d462b5a1229df8961e55f72770c4a32a7f021835c774509cfa0

Tx prefix hash: 8fbfca0d470351e40a2e74e4d65bb59f1790c66613b54de0dade4baac390c246
Tx public key: 51fc25087ecc773f6d2845aa99554d6c8ca8e9128ac0671fc968c20d78bad1ee
Timestamp: 1588736724 Timestamp [UCT]: 2020-05-06 03:45:24 Age [y:d:h:m:s]: 04:305:11:40:24
Block: 98968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134513 RingCT/type: yes/0
Extra: 0151fc25087ecc773f6d2845aa99554d6c8ca8e9128ac0671fc968c20d78bad1ee02110000016f37fb5df4000000000000000000

1 output(s) for total of 288.503204819000 dcy

stealth address amount amount idx
00: d29aa5ea520db3591668cbef4167487dd8b64beb2454296af233c279724b2af6 288.503204819000 174788 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": 98978, "vin": [ { "gen": { "height": 98968 } } ], "vout": [ { "amount": 288503204819, "target": { "key": "d29aa5ea520db3591668cbef4167487dd8b64beb2454296af233c279724b2af6" } } ], "extra": [ 1, 81, 252, 37, 8, 126, 204, 119, 63, 109, 40, 69, 170, 153, 85, 77, 108, 140, 168, 233, 18, 138, 192, 103, 31, 201, 104, 194, 13, 120, 186, 209, 238, 2, 17, 0, 0, 1, 111, 55, 251, 93, 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