Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1f897dfd08bcb116974fa12ec69076b5d549bfd2081884c6db298dce40d4a2

Tx prefix hash: 74823bb6ebc05f1f224b112f20f0419e3a73bea52e90fd0287ecad5e35fa86da
Tx public key: c040b5652f46d5cc15976aea0cafbc3aeaaba81f5ab058451fa1c32f4a4b5c4c
Timestamp: 1701168832 Timestamp [UCT]: 2023-11-28 10:53:52 Age [y:d:h:m:s]: 00:363:07:49:00
Block: 901434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260152 RingCT/type: yes/0
Extra: 01c040b5652f46d5cc15976aea0cafbc3aeaaba81f5ab058451fa1c32f4a4b5c4c021100000001faf35c9c000000000000000000

1 output(s) for total of 0.632666642000 dcy

stealth address amount amount idx
00: d5089a237ceebab945027469d90d4da6dd8abac4b86a1601dfcff11476df2e8b 0.632666642000 1357997 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": 901444, "vin": [ { "gen": { "height": 901434 } } ], "vout": [ { "amount": 632666642, "target": { "key": "d5089a237ceebab945027469d90d4da6dd8abac4b86a1601dfcff11476df2e8b" } } ], "extra": [ 1, 192, 64, 181, 101, 47, 70, 213, 204, 21, 151, 106, 234, 12, 175, 188, 58, 234, 171, 168, 31, 90, 176, 88, 69, 31, 161, 195, 47, 74, 75, 92, 76, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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