Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ac2a1b5e182500a5b4fb1aeea2ec25aa5f8e801ed5eceb8a17907c0615318a

Tx prefix hash: 41aed790c617af4c63ba9af39caba325a84518b9350f358f95c15af1362bb970
Tx public key: 0c908dfcb0bb699f45a0130b55678f678739fba6c4a9159a24dfbbf833af7613
Timestamp: 1708770379 Timestamp [UCT]: 2024-02-24 10:26:19 Age [y:d:h:m:s]: 01:270:19:37:31
Block: 964464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452282 RingCT/type: yes/0
Extra: 010c908dfcb0bb699f45a0130b55678f678739fba6c4a9159a24dfbbf833af761302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 227ca79f9f12f04facf1a4ab5fde9a88f11e2b2360757ededfe470dcd26205f3 0.600000000000 1424205 of 15

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": 964474, "vin": [ { "gen": { "height": 964464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "227ca79f9f12f04facf1a4ab5fde9a88f11e2b2360757ededfe470dcd26205f3" } } ], "extra": [ 1, 12, 144, 141, 252, 176, 187, 105, 159, 69, 160, 19, 11, 85, 103, 143, 103, 135, 57, 251, 166, 196, 169, 21, 154, 36, 223, 187, 248, 51, 175, 118, 19, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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