Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0ecfd37405c3542a56b71ceda973c753996e81919b0e18f510135304c263e3

Tx prefix hash: 352c45f7a03c823ccf793f242ccbe7c1d00ba790b48739c96a02a46f6aac2bef
Tx public key: f8439363ef6e9bec5d33c9a470078af4ee8331f251e6bb5c44f194ac5cb0b9be
Timestamp: 1577492959 Timestamp [UCT]: 2019-12-28 00:29:19 Age [y:d:h:m:s]: 05:001:17:34:10
Block: 33143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151311 RingCT/type: yes/0
Extra: 01f8439363ef6e9bec5d33c9a470078af4ee8331f251e6bb5c44f194ac5cb0b9be021100000010d81c26c0000000000000000000

1 output(s) for total of 476.633255331000 dcy

stealth address amount amount idx
00: 404fe4b860e4b186bc0b3c4eaf9302d1df40d124ab8d7c5851364c13a055f654 476.633255331000 55374 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": 33153, "vin": [ { "gen": { "height": 33143 } } ], "vout": [ { "amount": 476633255331, "target": { "key": "404fe4b860e4b186bc0b3c4eaf9302d1df40d124ab8d7c5851364c13a055f654" } } ], "extra": [ 1, 248, 67, 147, 99, 239, 110, 155, 236, 93, 51, 201, 164, 112, 7, 138, 244, 238, 131, 49, 242, 81, 230, 187, 92, 68, 241, 148, 172, 92, 176, 185, 190, 2, 17, 0, 0, 0, 16, 216, 28, 38, 192, 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