Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449e44688351dc7cff417bec45e111e62df15e9c55592770350ffd8d54c35321

Tx prefix hash: 4704ae3df452a8396e22a368d4f3c473b3b8a3d9d7d21a409a0d5899462564e6
Tx public key: 1187c7219703dce9e789967b428cb9882e05bf04790c978481b3a93f68d47e3e
Timestamp: 1695578073 Timestamp [UCT]: 2023-09-24 17:54:33 Age [y:d:h:m:s]: 01:186:15:41:13
Block: 855283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394463 RingCT/type: yes/0
Extra: 011187c7219703dce9e789967b428cb9882e05bf04790c978481b3a93f68d47e3e021100000005faf35c9c000000000000000000

1 output(s) for total of 0.899689030000 dcy

stealth address amount amount idx
00: 11acb73ae70aa70b53a9d29b9113031dc14069a7332d67059cf932aad2a6ba16 0.899689030000 1309297 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": 855293, "vin": [ { "gen": { "height": 855283 } } ], "vout": [ { "amount": 899689030, "target": { "key": "11acb73ae70aa70b53a9d29b9113031dc14069a7332d67059cf932aad2a6ba16" } } ], "extra": [ 1, 17, 135, 199, 33, 151, 3, 220, 233, 231, 137, 150, 123, 66, 140, 185, 136, 46, 5, 191, 4, 121, 12, 151, 132, 129, 179, 169, 63, 104, 212, 126, 62, 2, 17, 0, 0, 0, 5, 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