Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f37b668996debcd475263a90f5cee35110c7dbaa814a6613f880561ecb025b1

Tx prefix hash: 493a080e70dd82679bf30921e00c27630b5e5eab036c0987cb46b76abe6af5c7
Tx public key: 75f118f89f86f58da40bd6d8079d3351aaa0b5bbb866c26ef3e2ea6723e39efe
Timestamp: 1672678684 Timestamp [UCT]: 2023-01-02 16:58:04 Age [y:d:h:m:s]: 02:013:06:14:52
Block: 666106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531382 RingCT/type: yes/0
Extra: 0175f118f89f86f58da40bd6d8079d3351aaa0b5bbb866c26ef3e2ea6723e39efe02110000000252542ceb000000000000000000

1 output(s) for total of 3.809906092000 dcy

stealth address amount amount idx
00: e6089ad2d0fb0b28dc5fdff6959715eaea1cb5193420e0560604f7f5a9138013 3.809906092000 1107201 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": 666116, "vin": [ { "gen": { "height": 666106 } } ], "vout": [ { "amount": 3809906092, "target": { "key": "e6089ad2d0fb0b28dc5fdff6959715eaea1cb5193420e0560604f7f5a9138013" } } ], "extra": [ 1, 117, 241, 24, 248, 159, 134, 245, 141, 164, 11, 214, 216, 7, 157, 51, 81, 170, 160, 181, 187, 184, 102, 194, 110, 243, 226, 234, 103, 35, 227, 158, 254, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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