Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98dbd3b747efa42f866ef0bdd62773485f3f4ceb796128c0c117b747ffbb36ba

Tx prefix hash: de4f3b0b9d436d924603edb41ae9bfc9e02db3a03e5b6df8697d9911e2ac8abb
Tx public key: 5b164072f3f7b295547851c8c9e54365a69a2e30f219433d39769829b4258ba0
Timestamp: 1702142887 Timestamp [UCT]: 2023-12-09 17:28:07 Age [y:d:h:m:s]: 01:037:23:24:55
Block: 909516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288487 RingCT/type: yes/0
Extra: 015b164072f3f7b295547851c8c9e54365a69a2e30f219433d39769829b4258ba002110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50b785ee71a1089c82b7a800b4d7e87f287d59f5c7c01fd700e3c078e1716dcd 0.600000000000 1366609 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": 909526, "vin": [ { "gen": { "height": 909516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50b785ee71a1089c82b7a800b4d7e87f287d59f5c7c01fd700e3c078e1716dcd" } } ], "extra": [ 1, 91, 22, 64, 114, 243, 247, 178, 149, 84, 120, 81, 200, 201, 229, 67, 101, 166, 154, 46, 48, 242, 25, 67, 61, 57, 118, 152, 41, 180, 37, 139, 160, 2, 17, 0, 0, 0, 1, 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