Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 001f1891d1de6a4627d74349a917544bdbe998d3c40673fa940624f32e658506

Tx prefix hash: 8cb26392b3ccf15bd90e1de788a8d2f9e9f25c1dcbc3d14bd2aa8aaf33b18629
Tx public key: 8bf186e40a64b49dc673a99766b1331aad6e344b202fc01b89c3271c64a7e331
Timestamp: 1656001668 Timestamp [UCT]: 2022-06-23 16:27:48 Age [y:d:h:m:s]: 02:357:18:56:42
Block: 528744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776757 RingCT/type: yes/0
Extra: 018bf186e40a64b49dc673a99766b1331aad6e344b202fc01b89c3271c64a7e3310211000000034da16a3a000000000000000000

1 output(s) for total of 10.865552119000 dcy

stealth address amount amount idx
00: 7fb32444d91519f8fe3238fa9a8df35e6ae744fad41a0762a51114a683dc6b93 10.865552119000 957601 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": 528754, "vin": [ { "gen": { "height": 528744 } } ], "vout": [ { "amount": 10865552119, "target": { "key": "7fb32444d91519f8fe3238fa9a8df35e6ae744fad41a0762a51114a683dc6b93" } } ], "extra": [ 1, 139, 241, 134, 228, 10, 100, 180, 157, 198, 115, 169, 151, 102, 177, 51, 26, 173, 110, 52, 75, 32, 47, 192, 27, 137, 195, 39, 28, 100, 167, 227, 49, 2, 17, 0, 0, 0, 3, 77, 161, 106, 58, 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