Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcdcb091b7171593723a73baed4eb9e99405902538a059dcc75f0388ee0239b1

Tx prefix hash: 4a46fae1360e1f24b4352cbaaeccdfb088d18286184491bc212e32607915927b
Tx public key: 8daf4d1c8d47f0a4d452e62ddb54d6b891ea7791c7f289514315ca1375717963
Timestamp: 1681256125 Timestamp [UCT]: 2023-04-11 23:35:25 Age [y:d:h:m:s]: 02:000:00:27:34
Block: 736579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522176 RingCT/type: yes/0
Extra: 018daf4d1c8d47f0a4d452e62ddb54d6b891ea7791c7f289514315ca1375717963021100000001b3164c24000000000000000000

1 output(s) for total of 2.225400736000 dcy

stealth address amount amount idx
00: 3e849d34c20212c839cc5044b3db0fe257fa1f979c7b8233c718e19ee1702445 2.225400736000 1183032 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": 736589, "vin": [ { "gen": { "height": 736579 } } ], "vout": [ { "amount": 2225400736, "target": { "key": "3e849d34c20212c839cc5044b3db0fe257fa1f979c7b8233c718e19ee1702445" } } ], "extra": [ 1, 141, 175, 77, 28, 141, 71, 240, 164, 212, 82, 230, 45, 219, 84, 214, 184, 145, 234, 119, 145, 199, 242, 137, 81, 67, 21, 202, 19, 117, 113, 121, 99, 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