Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb482c1d8050eab30c1ca3853a0b204b9b0a6d607a54e0d52d431a98d994159

Tx prefix hash: b35cde34ac00ae247b8a2a7215e12541408a8e13bcaf192a68da39ad55582fb4
Tx public key: ec974c0bfb1afaa25b02aec5f89578d306d4080e84d28b4c719e603e41a0c29a
Timestamp: 1725609589 Timestamp [UCT]: 2024-09-06 07:59:49 Age [y:d:h:m:s]: 00:204:06:23:31
Block: 1104069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145819 RingCT/type: yes/0
Extra: 01ec974c0bfb1afaa25b02aec5f89578d306d4080e84d28b4c719e603e41a0c29a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab8f4b9ef0741f87b446634a4fee4282576a0ee93ddddfe0a7f0105a1a5ef9e1 0.600000000000 1581128 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": 1104079, "vin": [ { "gen": { "height": 1104069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab8f4b9ef0741f87b446634a4fee4282576a0ee93ddddfe0a7f0105a1a5ef9e1" } } ], "extra": [ 1, 236, 151, 76, 11, 251, 26, 250, 162, 91, 2, 174, 197, 248, 149, 120, 211, 6, 212, 8, 14, 132, 210, 139, 76, 113, 158, 96, 62, 65, 160, 194, 154, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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