Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7dce075a140860e19ff3676b1f32b1eb95e8d1721f95962807c43f7885e1ff83

Tx prefix hash: 666b8ea1fa394a210516afc182a81ec719e6252f1a583dbf985042592c4dd09b
Tx public key: 0439320b7cc4266d3c1d95e8af1ea0d439391fcd38416a4576f175c4fbbcbb76
Timestamp: 1585549639 Timestamp [UCT]: 2020-03-30 06:27:19 Age [y:d:h:m:s]: 05:044:16:13:42
Block: 89683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1191920 RingCT/type: yes/0
Extra: 010439320b7cc4266d3c1d95e8af1ea0d439391fcd38416a4576f175c4fbbcbb7602110000000e39be35fb000000000000000000

1 output(s) for total of 309.630523879000 dcy

stealth address amount amount idx
00: 291d52b83dbc6b68d6fef805642841df24f4375a0e27cfc406b3098d82cae8e4 309.630523879000 160835 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": 89693, "vin": [ { "gen": { "height": 89683 } } ], "vout": [ { "amount": 309630523879, "target": { "key": "291d52b83dbc6b68d6fef805642841df24f4375a0e27cfc406b3098d82cae8e4" } } ], "extra": [ 1, 4, 57, 50, 11, 124, 196, 38, 109, 60, 29, 149, 232, 175, 30, 160, 212, 57, 57, 31, 205, 56, 65, 106, 69, 118, 241, 117, 196, 251, 188, 187, 118, 2, 17, 0, 0, 0, 14, 57, 190, 53, 251, 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