Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8de031ca8754c4308d24cdd50ecc31363f299cc36395d20062b6272e4ccedd9

Tx prefix hash: fb5fd674d75b0ecb1a8d4756f2a978f0ec28b63ed4ec77d6ccd92e7bb2e28f44
Tx public key: c29d0cb660e37b270527c3e9c604118c58edd7852d6f2758b6155dd7a75a80f3
Timestamp: 1734191372 Timestamp [UCT]: 2024-12-14 15:49:32 Age [y:d:h:m:s]: 00:101:10:17:41
Block: 1175116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72250 RingCT/type: yes/0
Extra: 01c29d0cb660e37b270527c3e9c604118c58edd7852d6f2758b6155dd7a75a80f3021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7cbf5d088602505147aad297652f86394830b762d2e473fc4a7c70f6f415d08 0.600000000000 1661351 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": 1175126, "vin": [ { "gen": { "height": 1175116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7cbf5d088602505147aad297652f86394830b762d2e473fc4a7c70f6f415d08" } } ], "extra": [ 1, 194, 157, 12, 182, 96, 227, 123, 39, 5, 39, 195, 233, 198, 4, 17, 140, 88, 237, 215, 133, 45, 111, 39, 88, 182, 21, 93, 215, 167, 90, 128, 243, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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