Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1303d5e9a6904714702afd85714ac2f0d4d3a364a71ae2cc2342e9f0499e053

Tx prefix hash: 44073de7c2d28d41de74cd5b191e19e202de87351b1c4e7623e686a15740fa50
Tx public key: f47db37570c40bbc8f784169987cf75dbdaad039b3c669715c8bd6dc219a67a3
Timestamp: 1711138658 Timestamp [UCT]: 2024-03-22 20:17:38 Age [y:d:h:m:s]: 01:019:12:18:56
Block: 984114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274905 RingCT/type: yes/0
Extra: 01f47db37570c40bbc8f784169987cf75dbdaad039b3c669715c8bd6dc219a67a302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 596dba4fd49f29dde052d0b70a9e0c2f17c5fc4be69664e56218dc67fd4052d6 0.600000000000 1444269 of 15

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": 984124, "vin": [ { "gen": { "height": 984114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "596dba4fd49f29dde052d0b70a9e0c2f17c5fc4be69664e56218dc67fd4052d6" } } ], "extra": [ 1, 244, 125, 179, 117, 112, 196, 11, 188, 143, 120, 65, 105, 152, 124, 247, 93, 189, 170, 208, 57, 179, 198, 105, 113, 92, 139, 214, 220, 33, 154, 103, 163, 2, 17, 0, 0, 0, 2, 82, 212, 126, 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