Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47570333f7e91135e8f75316d2ac2eee16eeb70b7ddbb572f4c9349540120a72

Tx prefix hash: 1037c86d2fa52f65afcbf32aba0abc86cc4d17edd7240b54dd2a2aa71c20f21d
Tx public key: dfe61a2ab2968190c1360b29f396a002d2a6ae47bf409cc6f92cd163c3f9c1b3
Timestamp: 1694059309 Timestamp [UCT]: 2023-09-07 04:01:49 Age [y:d:h:m:s]: 01:263:13:11:56
Block: 842675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449505 RingCT/type: yes/0
Extra: 01dfe61a2ab2968190c1360b29f396a002d2a6ae47bf409cc6f92cd163c3f9c1b302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.990530793000 dcy

stealth address amount amount idx
00: c4a4b40d5d6b2f24c90705b428ab447f388e473ab37ddefc047d62f0b15c0b8d 0.990530793000 1295817 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": 842685, "vin": [ { "gen": { "height": 842675 } } ], "vout": [ { "amount": 990530793, "target": { "key": "c4a4b40d5d6b2f24c90705b428ab447f388e473ab37ddefc047d62f0b15c0b8d" } } ], "extra": [ 1, 223, 230, 26, 42, 178, 150, 129, 144, 193, 54, 11, 41, 243, 150, 160, 2, 210, 166, 174, 71, 191, 64, 156, 198, 249, 44, 209, 99, 195, 249, 193, 179, 2, 17, 0, 0, 0, 7, 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