Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f61f53139daf07c76b58737f4857c767b3c3e5d4dbf31218b0fdf5e73bab9bd2

Tx prefix hash: dc0fb9155ee7bf0ff3ac073aa01622810c246aa9b60f1c320b8c5420ab3bc4bd
Tx public key: 5c0acd60e5387cd917110e705af922362a7cd289297633e4fa4b999fb1c3b304
Timestamp: 1681782700 Timestamp [UCT]: 2023-04-18 01:51:40 Age [y:d:h:m:s]: 02:010:16:17:53
Block: 740955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529790 RingCT/type: yes/0
Extra: 015c0acd60e5387cd917110e705af922362a7cd289297633e4fa4b999fb1c3b3040211000000025029cbac000000000000000000

1 output(s) for total of 2.152329293000 dcy

stealth address amount amount idx
00: f15a86ed2d9a8489e893a65439a785a91f4a43f2ae76febdfe33517706fe5be2 2.152329293000 1187866 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": 740965, "vin": [ { "gen": { "height": 740955 } } ], "vout": [ { "amount": 2152329293, "target": { "key": "f15a86ed2d9a8489e893a65439a785a91f4a43f2ae76febdfe33517706fe5be2" } } ], "extra": [ 1, 92, 10, 205, 96, 229, 56, 124, 217, 23, 17, 14, 112, 90, 249, 34, 54, 42, 124, 210, 137, 41, 118, 51, 228, 250, 75, 153, 159, 177, 195, 179, 4, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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