Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 921e33115c6a4502539bb34550abcc30f19386264278b02f8f158f085f079b03

Tx prefix hash: 33f9ba681dcf31cb5c45ddf17d7688e62d5bb5ef7d42f97c9e1cde80ce8d66bd
Tx public key: df6b9b9e9a3c46ca3b944469b1f8b7ccfbe59e019d0702cefdc1789d63d53635
Timestamp: 1684120694 Timestamp [UCT]: 2023-05-15 03:18:14 Age [y:d:h:m:s]: 02:186:15:36:27
Block: 760357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653209 RingCT/type: yes/0
Extra: 01df6b9b9e9a3c46ca3b944469b1f8b7ccfbe59e019d0702cefdc1789d63d53635021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.856187346000 dcy

stealth address amount amount idx
00: 57a507788bbf26376c8c7369edafd77336b2b48e6f55c5ba97473e8f2582a52d 1.856187346000 1208960 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": 760367, "vin": [ { "gen": { "height": 760357 } } ], "vout": [ { "amount": 1856187346, "target": { "key": "57a507788bbf26376c8c7369edafd77336b2b48e6f55c5ba97473e8f2582a52d" } } ], "extra": [ 1, 223, 107, 155, 158, 154, 60, 70, 202, 59, 148, 68, 105, 177, 248, 183, 204, 251, 229, 158, 1, 157, 7, 2, 206, 253, 193, 120, 157, 99, 213, 54, 53, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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