Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f631204193a0b16c8c2e3e80080bb0ba3717f7794f0b2b512f0483d3a5652001

Tx prefix hash: 179667d01509029a367f775e7fe969c00e1d446a2e21d9be8fa4088a7daa8e54
Tx public key: bf7772a4e4ce50422712657397683fdcf10f55a74cda06acddbc0ff135c9f6aa
Timestamp: 1628921659 Timestamp [UCT]: 2021-08-14 06:14:19 Age [y:d:h:m:s]: 03:204:12:03:05
Block: 313690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 919151 RingCT/type: yes/0
Extra: 01bf7772a4e4ce50422712657397683fdcf10f55a74cda06acddbc0ff135c9f6aa021100000011e6f80b5a000000000000000000

1 output(s) for total of 56.056089342000 dcy

stealth address amount amount idx
00: 44f232947954a1cde22ea72c609d18b3257f9f878c87224814a05b027ed227b1 56.056089342000 652889 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": 313700, "vin": [ { "gen": { "height": 313690 } } ], "vout": [ { "amount": 56056089342, "target": { "key": "44f232947954a1cde22ea72c609d18b3257f9f878c87224814a05b027ed227b1" } } ], "extra": [ 1, 191, 119, 114, 164, 228, 206, 80, 66, 39, 18, 101, 115, 151, 104, 63, 220, 241, 15, 85, 167, 76, 218, 6, 172, 221, 188, 15, 241, 53, 201, 246, 170, 2, 17, 0, 0, 0, 17, 230, 248, 11, 90, 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