Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9aa58174998c6a74b90c07e05efeee402032af34a367684eef9146c5754a74c2

Tx prefix hash: 256799dcf83c66e1d6cdc7ba8eae162ec3e589536908b30943e61ff07bd4c183
Tx public key: ca92405bd3a8bd4f715eeae90591c610866418b66b0866b1511344d21c526e00
Timestamp: 1700986015 Timestamp [UCT]: 2023-11-26 08:06:55 Age [y:d:h:m:s]: 01:202:19:01:19
Block: 899915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406058 RingCT/type: yes/0
Extra: 01ca92405bd3a8bd4f715eeae90591c610866418b66b0866b1511344d21c526e0002110000000575e3f0e9000000000000000000

1 output(s) for total of 0.640041326000 dcy

stealth address amount amount idx
00: 0ffcc2e9805ee4bb03008225324cb7c5eb31f86834fb62235ffb28d0e2818d7b 0.640041326000 1356384 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": 899925, "vin": [ { "gen": { "height": 899915 } } ], "vout": [ { "amount": 640041326, "target": { "key": "0ffcc2e9805ee4bb03008225324cb7c5eb31f86834fb62235ffb28d0e2818d7b" } } ], "extra": [ 1, 202, 146, 64, 91, 211, 168, 189, 79, 113, 94, 234, 233, 5, 145, 198, 16, 134, 100, 24, 182, 107, 8, 102, 177, 81, 19, 68, 210, 28, 82, 110, 0, 2, 17, 0, 0, 0, 5, 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