Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 783889515c0a2fb5ab24f822064e5101109f536ce40420c9a18ccae690a4e8d2

Tx prefix hash: 78cb3c890c7b164d80a819d9f7ac573b658e0a45dfd58af40920f55e25434e43
Tx public key: fc88dcd00aeb2e425d1ccda9841d6fea334efacb5d2979bbd640d2941af80bc6
Timestamp: 1632866157 Timestamp [UCT]: 2021-09-28 21:55:57 Age [y:d:h:m:s]: 03:091:10:24:26
Block: 342783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 842108 RingCT/type: yes/0
Extra: 01fc88dcd00aeb2e425d1ccda9841d6fea334efacb5d2979bbd640d2941af80bc60211000000023fc41461000000000000000000

1 output(s) for total of 44.897075784000 dcy

stealth address amount amount idx
00: 7ec1f9e8824534d7ea43b7ee8c65c9534400b4971d5a274b5834b284776faf61 44.897075784000 703873 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": 342793, "vin": [ { "gen": { "height": 342783 } } ], "vout": [ { "amount": 44897075784, "target": { "key": "7ec1f9e8824534d7ea43b7ee8c65c9534400b4971d5a274b5834b284776faf61" } } ], "extra": [ 1, 252, 136, 220, 208, 10, 235, 46, 66, 93, 28, 205, 169, 132, 29, 111, 234, 51, 78, 250, 203, 93, 41, 121, 187, 214, 64, 210, 148, 26, 248, 11, 198, 2, 17, 0, 0, 0, 2, 63, 196, 20, 97, 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