Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f61d03f5549d552b3ac8e4b85169a5a6e275d604ce34029fa2497a80dce8d3

Tx prefix hash: 25d55378977c5509ea827492fbf1a59934b0842e16a0febfc133da47a47cc43a
Tx public key: 97e9a09d8075c861bfa8fb86e4dd8f139fa1e028972061a5219d4d8297fa4ccc
Timestamp: 1694803531 Timestamp [UCT]: 2023-09-15 18:45:31 Age [y:d:h:m:s]: 01:130:07:51:19
Block: 848851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354415 RingCT/type: yes/0
Extra: 0197e9a09d8075c861bfa8fb86e4dd8f139fa1e028972061a5219d4d8297fa4ccc0211000000104b8f5122000000000000000000

1 output(s) for total of 0.944940190000 dcy

stealth address amount amount idx
00: dd4d5e7eba8b7444782a5996d46377ff7feca52864a90be1743d0793dd604ed9 0.944940190000 1302481 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": 848861, "vin": [ { "gen": { "height": 848851 } } ], "vout": [ { "amount": 944940190, "target": { "key": "dd4d5e7eba8b7444782a5996d46377ff7feca52864a90be1743d0793dd604ed9" } } ], "extra": [ 1, 151, 233, 160, 157, 128, 117, 200, 97, 191, 168, 251, 134, 228, 221, 143, 19, 159, 161, 224, 40, 151, 32, 97, 165, 33, 157, 77, 130, 151, 250, 76, 204, 2, 17, 0, 0, 0, 16, 75, 143, 81, 34, 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