Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1fa78e5709c5627e35dc1a9d7da70b2fd94067b7ea7516411a59f4267091f73

Tx prefix hash: a8cc207104de78c9fda056ee0d2e89bacd08747227810bc994a6307ba48efb48
Tx public key: 929f80efbdd3fffe731c874c3a764e92438e54cc22f9857f5ae92f9ba394f65d
Timestamp: 1711749829 Timestamp [UCT]: 2024-03-29 22:03:49 Age [y:d:h:m:s]: 00:333:02:24:30
Block: 989175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238113 RingCT/type: yes/0
Extra: 01929f80efbdd3fffe731c874c3a764e92438e54cc22f9857f5ae92f9ba394f65d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c93fa6029c7cd72e978a0364d691d766bf1b6170c2ca61c6795540fbd3de038 0.600000000000 1449470 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": 989185, "vin": [ { "gen": { "height": 989175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c93fa6029c7cd72e978a0364d691d766bf1b6170c2ca61c6795540fbd3de038" } } ], "extra": [ 1, 146, 159, 128, 239, 189, 211, 255, 254, 115, 28, 135, 76, 58, 118, 78, 146, 67, 142, 84, 204, 34, 249, 133, 127, 90, 233, 47, 155, 163, 148, 246, 93, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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