Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa1f5ca5b18dbd99cbc1790183640d6036de78ce209e0b12c8ace9dbd186fc6

Tx prefix hash: cfed166fc0abb40a36469cc384f4a986c008208b28bc0d2e105bebf84339cbbc
Tx public key: 7b47c856a01e6a2cb7768d4fc58fca67eabe8a7c0fecc17d062b5ef85379287b
Timestamp: 1686387424 Timestamp [UCT]: 2023-06-10 08:57:04 Age [y:d:h:m:s]: 01:214:19:22:58
Block: 779145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414916 RingCT/type: yes/0
Extra: 017b47c856a01e6a2cb7768d4fc58fca67eabe8a7c0fecc17d062b5ef85379287b02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.608308425000 dcy

stealth address amount amount idx
00: 503c05ccf4fe08d7ea4655a3e24afe615acaacbeda5be3765e0197758d4728e1 1.608308425000 1228790 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": 779155, "vin": [ { "gen": { "height": 779145 } } ], "vout": [ { "amount": 1608308425, "target": { "key": "503c05ccf4fe08d7ea4655a3e24afe615acaacbeda5be3765e0197758d4728e1" } } ], "extra": [ 1, 123, 71, 200, 86, 160, 30, 106, 44, 183, 118, 141, 79, 197, 143, 202, 103, 234, 190, 138, 124, 15, 236, 193, 125, 6, 43, 94, 248, 83, 121, 40, 123, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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