Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c2912f92865fa614dfb545cfafdfad610f5ceec2bea76690ef072e2b563fcde

Tx prefix hash: b04c8683f24a114a0a4f49b159712675c07523bc88557035ff45f3cef193d239
Tx public key: 3e4c40435594544df6a0d6262bcce529fd303af6fb8de99610237c0810b765c8
Timestamp: 1681181298 Timestamp [UCT]: 2023-04-11 02:48:18 Age [y:d:h:m:s]: 02:002:13:56:36
Block: 735966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524007 RingCT/type: yes/0
Extra: 013e4c40435594544df6a0d6262bcce529fd303af6fb8de99610237c0810b765c8021100000001b3164c24000000000000000000

1 output(s) for total of 2.235832948000 dcy

stealth address amount amount idx
00: 27809adb5b872ca0d2bb49d8804ef84a894bbf93a29a184b21b63fe5a752e818 2.235832948000 1182339 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": 735976, "vin": [ { "gen": { "height": 735966 } } ], "vout": [ { "amount": 2235832948, "target": { "key": "27809adb5b872ca0d2bb49d8804ef84a894bbf93a29a184b21b63fe5a752e818" } } ], "extra": [ 1, 62, 76, 64, 67, 85, 148, 84, 77, 246, 160, 214, 38, 43, 204, 229, 41, 253, 48, 58, 246, 251, 141, 233, 150, 16, 35, 124, 8, 16, 183, 101, 200, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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