Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e713069ccae943025d01391bae1095511b9278765cf927c178d0679c321d8e

Tx prefix hash: e8f36efcd955b0b5a360076e8327adbfc3fe69c98d54706f307343d09a322638
Tx public key: 2aa1f642fab8a70a3a4706bae17dad8b2c614d778f587337b55df3c9dca9e785
Timestamp: 1701590104 Timestamp [UCT]: 2023-12-03 07:55:04 Age [y:d:h:m:s]: 01:181:16:34:26
Block: 904929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391063 RingCT/type: yes/0
Extra: 012aa1f642fab8a70a3a4706bae17dad8b2c614d778f587337b55df3c9dca9e78502110000000275e3f0e9000000000000000000

1 output(s) for total of 0.616019621000 dcy

stealth address amount amount idx
00: 58d6fb3291e523276629d7baff354e52f719285dc2d12f0da80864203ac482a1 0.616019621000 1361714 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": 904939, "vin": [ { "gen": { "height": 904929 } } ], "vout": [ { "amount": 616019621, "target": { "key": "58d6fb3291e523276629d7baff354e52f719285dc2d12f0da80864203ac482a1" } } ], "extra": [ 1, 42, 161, 246, 66, 250, 184, 167, 10, 58, 71, 6, 186, 225, 125, 173, 139, 44, 97, 77, 119, 143, 88, 115, 55, 181, 93, 243, 201, 220, 169, 231, 133, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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