Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb3cfc4e3829bfc619da6c40715e8c1bd095644715d4ae83c48bded8410357b

Tx prefix hash: a840222e50ea337896accfed645e939486410923bc02eccf2658eb353d053043
Tx public key: 7ff54938214402a804cc32e6acb2b22e9ca11326a4de192fc6058b0afb37d0e2
Timestamp: 1578655155 Timestamp [UCT]: 2020-01-10 11:19:15 Age [y:d:h:m:s]: 05:090:12:07:15
Block: 42570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214733 RingCT/type: yes/0
Extra: 017ff54938214402a804cc32e6acb2b22e9ca11326a4de192fc6058b0afb37d0e202110000000c4ac5aa02000000000000000000

1 output(s) for total of 443.556310360000 dcy

stealth address amount amount idx
00: 8260e832bdf076f4994283281d89a92794079dcbfa435f3bca5d13ccea03d6c0 443.556310360000 76746 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": 42580, "vin": [ { "gen": { "height": 42570 } } ], "vout": [ { "amount": 443556310360, "target": { "key": "8260e832bdf076f4994283281d89a92794079dcbfa435f3bca5d13ccea03d6c0" } } ], "extra": [ 1, 127, 245, 73, 56, 33, 68, 2, 168, 4, 204, 50, 230, 172, 178, 178, 46, 156, 161, 19, 38, 164, 222, 25, 47, 198, 5, 139, 10, 251, 55, 208, 226, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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