Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc440fb8ea45bbb4b9559fcc1b27f7ffd7a8cc5d3455723cabd8430c29922f02

Tx prefix hash: 660682f93457b4d9d60d5e2ebd9b082740fa8385ace5247f2111032197f849a9
Tx public key: 529034a90a0f3c06b45b9a629c9f62ae739fe53385060f08df37e15358bd6107
Timestamp: 1725347333 Timestamp [UCT]: 2024-09-03 07:08:53 Age [y:d:h:m:s]: 00:270:02:38:33
Block: 1101891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192940 RingCT/type: yes/0
Extra: 01529034a90a0f3c06b45b9a629c9f62ae739fe53385060f08df37e15358bd6107021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e64ae90a44a6bc5ea223e7acdd719c7b2fdcbcfb2fa79159ee90cb7355139906 0.600000000000 1578112 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": 1101901, "vin": [ { "gen": { "height": 1101891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e64ae90a44a6bc5ea223e7acdd719c7b2fdcbcfb2fa79159ee90cb7355139906" } } ], "extra": [ 1, 82, 144, 52, 169, 10, 15, 60, 6, 180, 91, 154, 98, 156, 159, 98, 174, 115, 159, 229, 51, 133, 6, 15, 8, 223, 55, 225, 83, 88, 189, 97, 7, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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